I don't think this is required. The problem is with syncing the column names. Normal columns works without any extra variables.

The isInclude variable helps track which columns are added to the "Include Column" field in the create table modal, especially when column names change. This works similarly to the is_primary_key variable that tracks columns in the model's column field. This helps maintain proper tracking of column states. Let me know if you'd prefer a different approach!

I don't see any is_foreign_key or is_unique_key variables. I don't think it is the right direction.

Then what is the use of include_columns key?